In Quick Fields 8, tokens can be customized to extract particular pieces of data from the information retrieved or to use particular formatting.
To customize a token:
Note: To use Pattern Matching expressions, you must have the Pattern Matching add-on installed.
The format for a token that includes a regular expression is %(Token#<regex>#).
Example: Jonathan wants to fill out a field with the day and month a document was processed, but not the year. He inserts the standard Date token in the field, which would result in entries that are named similarly to: 2/8/2009. He opens the token editor and inserts the regular expression \d.\d. This results in entries that are named similar to 2/8.
Example: Misty is scanning documents that include multiple barcodes containing various pieces of information. When she configured her barcode process, she set it to read the whole page rather than individual zones. Her token from that process contains the values from all the barcodes on the page. She wants to extract only the value from the second barcode on the page, so she specifies the index 2 representing the second barcode.
If the index is a number, it will return that index of a multi-valued token.
1, 1st value/line etc,
-1, last value/line etc,
2 2nd line
-2 2nd to last line
0 does nothing
If the index is not a number, it will join all values.
So if the join is the value “; “ and your token is
1
2
3
The result would be 1; 2; 3.
The format for a token that includes an index is: %(Token#[index]#)
The format for a formatted token is %(Token,”tokenformat”).
You can use standard format constraints.
Example: Including the formatting d MMMM, yyyy would yield the formatted token %(Date,"d MMMM, yyyy"). When the value 04/15/2009 is entered in the token, the value returned will be 15 April, 2009.
If your token name contains special characters such as , ( ) # < and so on, you can enclose the token name with [ ].
For further help or feedback, please see the Laserfiche Support Site. | © 2009 Laserfiche. All Rights Reserved. |